-
Notifications
You must be signed in to change notification settings - Fork 512
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: move toolkit to monorepo structure #4342
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
/runIntegrationTests |
90dc07d
to
c83b47b
Compare
c83b47b
to
aa81e7b
Compare
a906f33
to
084fef2
Compare
9a951c9
to
d0e2c38
Compare
16b28e1
to
4b0ff9f
Compare
4b0ff9f
to
81740b2
Compare
…to restructure3
9adfaf5
to
736cb47
Compare
736cb47
to
64c98e5
Compare
@@ -26,7 +26,7 @@ import { getTestWindow, resetTestWindow } from './shared/vscode/window' | |||
import { mapTestErrors, normalizeError, setRunnableTimeout } from './setupUtil' | |||
import { TelemetryDebounceInfo } from '../shared/vscode/commands2' | |||
|
|||
const testReportDir = join(__dirname, '../../../.test-reports') | |||
const testReportDir = join(__dirname, '../../../../../.test-reports') // Root project, not subproject |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Future: should concepts like globalSetup.test.ts
should be shared ? They solve lots of edge-cases and copy-pasting that across the subprojects adds quality risk.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes there should be a shared test setup function/library in a commons folder. Will document.
/runintegrationtests |
These commits restructure our project into a monorepo. Using npm workspaces. The original toolkit extension code now lives under
packages/toolkit/
. Additional extensions and common modules will go under thepackages/
folder. From this point on, you will need to be more specific with how you run npm scripts. I have added passthroughs for many of the npm scripts in the root folder, e.g.npm run compile
andnpm run test
. But other lesser used commands may need to be accessed by first going to the subproject directory. Additionally, to run VSCode run and debug configs, you will need to set the subproject folder as your root folder in VSCode (or add it as root folder).Consult https://github.com/aws/aws-toolkit-vscode/blob/21c66e259c88f8c0ca54f8aaff010c301668c683/docs/ARCHITECTURE.md#monorepo-structure for more info on this change.
Remaining work items:
Get VSCode debugging configurations to workFix Github Action-based CI entry points.Ensure coverage works properlyMerge conflicts :((Required after merge?) Fix packaging CILicense
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.